# Which PLM software keeps the bill of materials accurate across multiple design revisions without engineers having to manually reconcile changes?

<p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">I am looking for input on <a class="a a--md" elv="true" href="https://www.g2.com/categories/product-lifecycle-management-plm">product lifecycle management (PLM) software</a>, specifically on BOM accuracy across design revisions, the specific failure mode where a design change in CAD doesn't automatically propagate to the BOM, and engineers are manually reconciling two disconnected sources of truth, and production releases are built from a BOM that no longer reflects the actual design.</p><ol>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/openbom/reviews"><strong>OpenBOM</strong></a><strong>:</strong> CAD add-ins for SolidWorks, Fusion 360, and other tools automatically generate and update BOMs directly from CAD assemblies. Version tracking across multiple levels of the BOM allows teams to see the current version and trace back to previous states without digging through folder structures.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/siemens-teamcenter/reviews"><strong>Siemens Teamcenter</strong></a><strong>:</strong> BOM management is a primary daily use case, tracking parts and assemblies with a clear revision history that is easy to follow, identifying duplicate parts and flagging reuse opportunities, and automatically identifying impacted components when dependencies change. </li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/arena-plm/reviews"><strong>Arena PLM &amp; QMS</strong></a><strong>:</strong> BOM management with complete revision control is a core Arena capability. It can compare BOMs across revisions, identify exact changes between versions using the redline feature, and maintain where-used visibility for all components.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/duro/reviews"><strong>Duro</strong></a><strong>:</strong> BOM accuracy is maintained without requiring a dedicated PLM administrator to keep it clean. Designed for hardware startups and growing engineering teams that need BOM discipline from early in the product lifecycle rather than retrofitting it after the product is in production.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/aras-innovator/reviews"><strong>Aras Innovator</strong></a><strong>:</strong> The open platform architecture allows organizations to configure exactly how BOM changes propagate through the change management workflow, including the approval gates required before a BOM revision is released to manufacturing.</li>
</ol><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">For engineering teams that have dealt with BOM drift, at what point in the product lifecycle does the reconciliation cost become unsustainable? Is it during NPI when design is changing daily, during production when a BOM error triggers a recall, or during an audit when the history can't be reconstructed?</p>

##### Post Metadata
- Posted at: 3 months ago
- Author title: Marketing Executive
- Net upvotes: 1


## Comments
### Comment 1

&lt;p&gt;&lt;span style=&quot;color: rgb(0, 0, 0);&quot;&gt;For me it&#39;s the audit stage, not NPI, where reconciliation gets most painful. Nobody remembers the reasoning behind a revision from six months back, and that&#39;s exactly where Arena&#39;s redline comparison earns its keep, since you can see what changed between versions without relying on someone&#39;s memory. It turns what would otherwise be a guessing game into something you can actually point to when someone asks why a change was made.&lt;/span&gt;&lt;/p&gt;

##### Comment Metadata
- Posted at: 17 days ago
- Author title: Marketing



### Comment 2

&lt;p&gt;Building on my earlier point about discipline, I think the real test is what happens when changes are moving quickly during NPI. If the PLM automatically propagates revisions but engineers can still bypass the process, BOM drift probably just happens differently. Has anyone found approval gates that actually prevent that without slowing engineering down?&lt;/p&gt;

##### Comment Metadata
- Posted at: 21 days ago
- Author title: Writer



### Comment 3

&lt;p&gt;The reconciliation cost gets unsustainable during NPI for me, because that’s when revisions are moving fastest and manual checks multiply quickly. By production, a bad BOM is no longer just an admin problem — it can turn into scrap, delays, or rework.&lt;/p&gt;

##### Comment Metadata
- Posted at: 22 days ago
- Author title: Marketer



### Comment 4

&lt;p&gt;This usually isn’t just a PLM problem. If engineers are still making changes directly in CAD without thinking about downstream impact, even a good system won’t save you. The tools help, but discipline still does a lot of the work here.&lt;/p&gt;

##### Comment Metadata
- Posted at: 3 months ago
- Author title: Writer





## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4